From ad554e2b0dd2a17815f24cffdcdb300567aa0553 Mon Sep 17 00:00:00 2001
From: robertl <robertl>
Date: Thu, 30 Nov 2006 01:48:08 +0000
Subject: [PATCH] More manual breaks for long lines.

---
 xmldoc/chapters/datums.xml |  2 +-
 xmldoc/chapters/styles.xml | 32 +++++++++++++++++++-------------
 xmldoc/formats/nmea.xml    |  2 +-
 xmldoc/formats/xmapwpt.xml | 11 +++++++----
 4 files changed, 28 insertions(+), 19 deletions(-)

diff --git a/xmldoc/chapters/datums.xml b/xmldoc/chapters/datums.xml
index 3bc474445..202077d56 100644
--- a/xmldoc/chapters/datums.xml
+++ b/xmldoc/chapters/datums.xml
@@ -10,7 +10,7 @@ a datum for the output file.
 The following is a list of the datums supported by GPSBabel.
 </para>
 
-<simplelist columns="5">
+<simplelist columns="4">
 <member>Adindan</member>
 <member>AFG</member>
 <member>Ain-El-Abd</member>
diff --git a/xmldoc/chapters/styles.xml b/xmldoc/chapters/styles.xml
index fc8a209f1..2a80eb333 100644
--- a/xmldoc/chapters/styles.xml
+++ b/xmldoc/chapters/styles.xml
@@ -28,7 +28,9 @@ or want, you must tell GPSBabel to use the xcsv format and have the xcsv
 format use that file.  If you created a new style file called 
 "mystyle.style" and you want to write the  waypoints from
 a GPX file named "mine.gpx" to it, you would issue a command like:
-<screen format="linespecific">gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -f mine.new</screen>
+</para>
+<para><command>gpsbabel -i gpx -f mine.gpx -o xcsv,style=mystyle.style -f mine.new</command></para>
+<para>
 You might then examine <filename>mine.new</filename> to see if it met
 your expectations.  If not, you could continue to tweak 
 <filename>mystyle.style</filename> until it did, rerunning the above
@@ -74,8 +76,9 @@ PROLOGUE	Name	Latitude	Longitude	Description	URL	Type	Container	Diff	Terr
 
 #
 # INDIVIDUAL DATA FIELDS, IN ORDER OF APPEARANCE:
-# NOTE: MS S&amp;T ONLY IMPORTS DATA, IT DOESN'T EXPORT THIS ANYWHERE SO WE CAN
-#       HAVE OUR WAY WITH THE FORMATTING. 
+# NOTE: MS S&amp;T ONLY IMPORTS DATA, IT DOESN'T 
+#       EXPORT THIS ANYWHERE SO WE CAN HAVE OUR 
+#       WAY WITH THE FORMATTING. 
 #
 IFIELD	SHORTNAME, "", "%s"		# Name
 IFIELD	LAT_DECIMAL, "", "%f"		# Latitude
@@ -451,7 +454,7 @@ examples:
 <para>
 example:
 </para>
-<screen format="linespecific">   IFIELD SHORTNAME,"","%s"   # (write shortname in the output file)
+<screen format="linespecific">   IFIELD SHORTNAME,"","%s"
 </screen>
 </section>
 
@@ -465,7 +468,7 @@ example:
 <para>
 examples:
 </para>
-<screen format="linespecific">   IFIELD DESCRIPTION,"","%s" # (write description in the output file)
+<screen format="linespecific">   IFIELD DESCRIPTION,"","%s" 
 </screen>
 </section>
 
@@ -487,7 +490,7 @@ examples:
 <para>
 example:
 </para>
-<screen format="linespecific">   IFIELD URL,"","%s" #	(writes the URL in the output file)
+<screen format="linespecific">   IFIELD URL,"","%s"
 </screen>
 </section>
 
@@ -501,7 +504,7 @@ example:
 <para>
 example:
 </para>
-<screen format="linespecific">   IFIELD URL_LINK_TEXT,"","%s" # (writes link text in the output file)
+<screen format="linespecific">   IFIELD URL_LINK_TEXT,"","%s" 
 </screen>
 </section>
 
@@ -515,7 +518,7 @@ example:
 <para>
 example:
 </para>
-<screen format="linespecific">   IFIELD ICON_DESCR,"","%s" # (writes link text in the output file)
+<screen format="linespecific">   IFIELD ICON_DESCR,"","%s" 
 </screen>
 </section>
 
@@ -610,12 +613,15 @@ examples:
 <para>
 examples:
 </para>
-<screen format="linespecific">   IFIELD LAT_HUMAN_READABLE,"","%c %d %f"   # (writes N 31 40.000)
+<screen format="linespecific">
+   #  (writes N 31 40.000)
+   IFIELD LAT_HUMAN_READABLE,"","%c %d %f"   
+   #  (writes "31 deg 40.000 min N")
    IFIELD LAT_HUMAN_READABLE,"","%d deg %f min %c"
-                              #  (writes "31 deg 40.000 min N")
-          #  Note that this string will confuse the reading routine due 
-          #  to the letter "n" in "min" and the letter "e" in "deg."
-   IFIELD LAT_HUMAN_READABLE,"","%d %d %f%c" # (writes 31 40 00.000N)
+   #  Note that this string will confuse the reading routine due 
+   #  to the letter "n" in "min" and the letter "e" in "deg."
+   # (writes 31 40 00.000N)
+   IFIELD LAT_HUMAN_READABLE,"","%d %d %f%c" 
 </screen>
 </section>
 
diff --git a/xmldoc/formats/nmea.xml b/xmldoc/formats/nmea.xml
index 9bfc29a67..6fdc4d4ee 100644
--- a/xmldoc/formats/nmea.xml
+++ b/xmldoc/formats/nmea.xml
@@ -31,7 +31,7 @@ that work with NMEA-0183 formatted data include:
   <ulink url="http://www.commlinx.com.au/GPS_recorder.htm">CommLinx GPS recorder</ulink>
 </member>
 <member>
-  <ulink url="http://www.sparkfun.com/commerce/product_info.php?products_id=671">SparkFun GPS Datalogger</ulink>
+  <ulink url="http://www.sparkfun.com/">SparkFun GPS Datalogger</ulink>
 </member>
 </simplelist>  
 <para>
diff --git a/xmldoc/formats/xmapwpt.xml b/xmldoc/formats/xmapwpt.xml
index ff1f2fea3..aea6eb87d 100644
--- a/xmldoc/formats/xmapwpt.xml
+++ b/xmldoc/formats/xmapwpt.xml
@@ -43,16 +43,18 @@ folks, something as simple as:
 <para>
 will do the trick just fine.  
 </para>
-<programlisting format="linespecific">
+<programlisting>
 #!/full/path/to/perl
 $INPUTFILE = @ARGV[0];
 $TARGETDIR = @ARGV[1];
 $FILENAME  = @ARGV[2];
 
 if (! $FILENAME) {
-    print "Usage: xmap_split.pl INPUT_FILE OUTPUT_DIRECTORY FILENAME_BASE\n";
+    print "Usage: xmap_split.pl " . 
+	"INPUT_FILE OUTPUT_DIRECTORY FILENAME_BASE\n";
     print " (i.e. xmapl_split.pl points.wpt /tmp/points GPSB)\n";
-    print " (created GPSB0001-GPSBXXXX in /tmp/points/ from points.wpt)\n";
+    print " (created GPSB0001-GPSBXXXX " .
+	" in /tmp/points/ from points.wpt)\n";
     exit;
 }
 
@@ -62,7 +64,8 @@ while (&lt;INFILE&gt;) {
     $lc++;
     $filename = sprintf("%s/Gpsb%04d.wpt", $TARGETDIR, $lc);
 
-    open (OUTFILE, "&gt;$filename") || die "Cannot open $filename for write!\n";
+    open (OUTFILE, "&gt;$filename") || 
+	die "Cannot open $filename for write!\n";
 
     print OUTFILE $_;
 
-- 
2.30.2